Skip to content
This repository has been archived by the owner on May 24, 2024. It is now read-only.

manifest: Drop rpm-ostree by default #314

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

cgwalters
Copy link
Member

This came out of discussion in CentOS/centos-bootc-dev#27

Basically...I think what we should emphasize in the future is the combination of bootc and dnf.

There's no really strong reason to use rpm-ostree at container build time versus dnf. Now on the client side...well, here's the interesting thing; with transient root enabled, dnf install etc generally just works.

Of course, persistent changes don't. However, anyone who wants that can just dnf install rpm-ostree in their container builds.

There is one gap that's somewhat important which is kernel arguments. Because we haven't taught grubby do deal with ostree, and we don't have containers/bootc#255 to change kargs per machine outside of install time one will need to just hand-edit the configs in /boot/loader.

Another fallout from this is that ostree container goes away inside the booted host...and today actually this totally breaks bib until osbuild/bootc-image-builder#18 is fixed.

Probably bootc should grow the interception for that too optionally.

This came out of discussion in CentOS/centos-bootc-dev#27

Basically...I think what we should emphasize in the future
is the combination of `bootc` and `dnf`.

There's no really strong reason to use `rpm-ostree` at container
build time versus `dnf`.  Now on the *client* side...well,
here's the interesting thing; with transient root enabled,
`dnf install` etc generally just works.

Of course, *persistent* changes don't.  However, anyone who
wants that can just `dnf install rpm-ostree` in their container
builds.

There is one gap that's somewhat important which is kernel arguments.
Because we haven't taught `grubby` do deal with ostree, and
we don't have containers/bootc#255
to change kargs per machine outside of install time one will
need to just hand-edit the configs in `/boot/loader`.

Another fallout from this is that `ostree container` goes away
inside the booted host...and today actually this totally
breaks bib until osbuild/bootc-image-builder#18
is fixed.

Probably bootc should grow the interception for that too optionally.
@rhatdan
Copy link
Collaborator

rhatdan commented Mar 25, 2024

LGTM
What is up with this one?

@cgwalters
Copy link
Member Author

What is up with this one?

Basically blocked on:

Another fallout from this is that ostree container goes away inside the booted host...and today actually this totally breaks bib until osbuild/bootc-image-builder#18 is fixed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants